Worked last evening getting Tech to start shooting them through to completions.

The P/L on Selling and Delivering Auditing (HCO PL 28 Sept 71) tells why you have to audit a pc all at once whole program. Dribbling it out means repairs due to life upsets before the guy made it.

An org board is a list of hats with seniorities. The hats are in flow sequence.

So crowd it on and get a pc through. Then we’ll have some products for our coins.

A hat is a duty. It outlines the actions necessary to accomplish a production and receive what’s needed, change and route it.

A Product Officer has to name, want and get his products.

In theory the I/C holds all functions. When he doesn’t fully outline them they can’t be hatted. If they’re not hatted he wears them as an unknown fog. Simple as that.

This means one says, “You there. Joe Blow. Want him completed. All right get it DONE.” Product by product. There is no general “Audit these pcs.” “Get up the hours.” Hell, you never get a product that way.

What defines a hat is a product.

“You there, George Thunderbird. I want you through your Primary and onto and through course and classified. Get going, man, get going. Oh, you were told to weedle the toofle before you woofled by Dorance Doppler. Org Officer? Get that name — to F/MAA, get the cross orders the hell off my lines. Now you George Thunderbird, I want you through your Primary and onto and through course by 1 July. You got it? You got it now! Good. Well, get with it. Get going!” Note on clipboard: Org Off to get cross order by Dorance Doppler invest and report. “There’s your slip.” Note on progress bd. Geo Thunderbird HSDA 1 Jul. Now you Tobler Tomias, what’s the tale; how are you going? . . . Well standing there smoking and looking at the scenery isn’t going to do anything. If your girl doesn’t like you anymore the thing to do is drown your sorrows in the Primary RD. . . . Okay you are to be an Exp Dn. All right, that’s fine. I want you completed by 16 July. . . . I don’t care if that’s a 16-hour day. Let’s see, Primary RD by __________ and Class IV Acad by ___________ and __________ Yes that’s 16 July AT NOON. Man to hell with your PTPs. Get going, man.” And on the progress board. And from the board — “And here’s Bill Coal, he should be off the Primary today, where is he. All right Bill — ah, you made it that far. Now you’re on schedule. That’s great. HSDA. Get with it, man. You completed Primary 20 minutes ago and aren’t on the next course. Super!*Supervisor What the __________.”

If you count up the expected products you get the minimum number of hats. The steps to get the product is the hat. Products are also composed of lesser products, so hats can be enlarged. It’s what you designate as a product that makes a hat. It’s the importance of that product to others on the line that makes the hat’s importance.

That’s the way it goes for a Tech Prod Off. “We are finishing Agnes, Trop and Goshwiler today. Today. Yes today. Certified and offlines. Got it D of T? Well, do it!”

The completeness and size of the product make the seniority of the hat.

Push, debug, drive. Name it, want it, get it.

The overall product of a division determines the hat of the divisional officer. The lesser products that when combined make the overall product determine the rest of the division hats.

That’s the only way you ever get a product.

Until you can define in one go the overall product of a division you aren’t likely to be able to post any real part of its org board. For the product of hats of that div add up to the div product.

Sad but true.

When you see an unposted or unreal org board, the head of the div is not producing a product with that div, no matter how busy it all looks or how exhausting.

They don’t ever happen by themselves.

And all the public relations chatter in the world is not a product. I know this Product Officer beat.

It’s a piece of cake.

But it has to be DONE.

[Note: The original mimeo copies of this policy letter incorrectly labeled it as “Admin Know-How 38” which has been corrected in this issue.]